What's New in 11.2.1
The release of OIPA 11.2.1.0 includes the below enhanced features in the Rules Palette and OIPA application:
New Features
Group Customer Quote
OIPA supports creation of quotes for both Group Customers (prospective/existing). Group Customer Quote can be produced for both prospective and existing Group Customers via the new Group Customer Quote Screen. In the Quote Screen, the user can enter, submit, view and initiate processing of a quote. It stores Group Customer Quote info (configurable), Benefit information, member information (when required), Claim information (when required) and the quote result. User can calculate multiple versions of a quote and store it under a group customer. A quote can be created for an existing client via an activity.
| Business Rule Changes | Database Table Changes |
|
New Rules Added:
|
New Tables Added:
|
Enhancements
Comments Enhancement
OIPA provides an ability to add case level comments and attach documents to comments from the UI. A user can search and view a list of all case comments and comment history belonging to all applications in a single view ordered by date. A user can add new comments while viewing search results same as that of the search results. It provides security to control the user access on the Search, Add, View, Modify, and Delete a comment operations. A user can add case level comments using "Add Comment" button from the CommentSearchScreen.
- A new element <CaseComments> is added to the CommentsScreen business rule under the root element to define Comments available at the Case entity level.
- A new element <CaseComments> is added to the CommentsSearchScreen business rule under the root element to define Comments available at the Case entity level.
Comment Display/Entry Enhancement
- Display entire comment text within the comment table without opening the comment detail.
- Increased comment length to 4000 characters.
- Ability to add comments while viewing search results.
- The new comments should be of the same type as the search results.
| Business Rule Changes | Database Table Changes |
|
Modified Rules:
|
New Tables Added:
|
Impairments Enhancement
Impairment functionality is extended to be available for both the Policy Admin and NBU processing. Also, new rules were introduced and enhanced, which may be configured according to the business need.
- ImpairmentScreen rule: This rule may be configured to be available for both Policy Admin and NBU side of the application.
- ImpairmentSearchScreen:This business rule allows configuration of OIPA's Impairment Summary table. If this rule is not configured, a default table will be used to display the impairment summary summary or search results. The groups supported for configuration, if the columns are Policy, Client, Segment, SegmentName, Impairment and ImpairmentField.
- CopyToImpairmentFields:This new attached business rule can be attached to a transaction or requirement to allow one or more MathVariables to be copied from the activity/requirement to one or more impairment fields.
- UpdateImpairmentStatus: This new system rule is introduced to change the processed status of an impairment. Processing the transaction to which this business rule is attached will change the status of the impairment to the one specified in this rule. The status code values will come from AsCodeImpairmentStatus.
- AddImpairments: AddImpairment rule is enhanced to include the ability to create a segment level impairment and populate the dynamic fields of the impairments. Any impairments created via the activities using AddImpairment rule will be displayed on the impairment screen.
| Business Rule Changes | Database Table Changes |
|
New Rules:
Modified Rule:
|
New Tables Added:
|
Extended Context Information Support for Requirements Definition
The definition of Requirements now supports expansion of context. The new context may be used to populate fields if the section defines them or execute logic in ScreenMath or Actions if the section defines them. Three definition sections of Requirement Definition, Requirement Screen, Requirement status transition and Requirement Result, will have information added to their context data. Contexts are now included for:
- Policy data
- Client data
- Activity data
- Transaction data
- Requirement data
- RequirementDefinition data
| Business Rule Changes | Database Table Changes |
|
Modified Rules:
|
New Tables Added: N/A |
Deep Linking Enhancement
This feature provides the ability to configure navigation to a third party URL in OIPA. It allows presentation of an external URL navigation button on any screen in OIPA with dynamic fields. A new Field DataType called LinkExternal is implemented to provide a mechanism for a user to open a new browser window/tab with target URL defined in configuration.
Other Usability Enhancements
MultiFields Support at Plan Level Segments
OIPA will load multifields of plan and product level override of a segment even though a multifield is configured at plan levelSegmentName uses inheritance functionality and merges the SegmentName definitions of the Product and Plan hierarchy.
MultiFields Support for Final Action Screen
Final Action screen is enhanced to support multifields configured in an activity. The configuration is driven by the corresponding activity enabled on Final Action screen business rule.
Final Action Screen Enhancement for Activity Errors or Warnings
Final Action screen is modified to include tabs to show Errors and Warnings list configured as per Validate Expressions. Errors and warnings can be overridable as per configuration and will be available for all views in Final Action screen BR.
Data Intake Profile Transaction Processing Supports Overridable Errors
Data Intake processing is enhanced to allow a user to configure overridable errors via ValidateExpression BR. This rule also provides security for message overrides or interacts with a catalog to suggest fixes. When the rule ValidateExpression is attached to the file transaction, it will support the ability to configure overridable errors in transaction processing.
Restricting Access of Privileged Users Using Filters
This enhancement introduces Filter configuration to PolicyScreen, ClientScreen, GroupCustomerScreen & CaseScreen. With this configuration, it is possible to restrict access of few privileged user entities from selected security groups.